Business process development and run time tool

ABSTRACT

A process development and run time tool identifies dependent relationships between information sources and processes of an enterprise system at design time. The process development and run time tool determines a business value and business risk for each process and stores this information in an information source and process dependency table. The process development and run time tool determines if a particular information source is a critical business risk and if so adds redundancy for the critical risk information source and/or fault tolerance into the process design. An operating system assembles the dependent processes for run time evaluation. If a dependent information source fails at run time, the process development and run time tool identifies each process within the enterprise system that is dependent upon this failed information source. The process development and run time tool informs all stakeholders that rely on information from the failed information source, then prioritizes the elimination of failed information source defects that exceed a predetermined business risk threshold. The process development and run time tool may terminate at risk business processes that exceed a predetermined business risk threshold.

BACKGROUND

The disclosures herein relate generally to information handling systems(IHSs), and more specifically, to management of processes and respectivedependent information sources in an IHS.

Information handling systems (IHSs) typically employ operating systemsthat execute applications or other processes that may require theresources of one or more information sources. IHS operating systems mayexecute process development and run time tools that analyze or otherwiseevaluate the business risks that a particular process and respectivedependent information source exhibit in the case of process orinformation source failure. Business risk development may includeprocess development as well as the evaluation of business process riskswith respect to failures of respective information sources on which theprocesses depend.

BRIEF SUMMARY

In one embodiment, a computer implemented method is disclosed thatincludes forming at design time, by a process development and run timetool, a dependency table that includes a list of information sourceswith dependent processes. The dependency table also includes a list ofbusiness values, each business value corresponding to a respectivedependent process. The dependency table further includes a list ofbusiness risks, each business risk corresponding to a respectivedependent process. The dependency table still further includes arespective composite information source business risk for eachinformation source in the list of information sources. The methodincludes identifying at design time, by the process development and runtime tool, those information sources of the list of information sourcesthat exhibit a composite information source business risk that exceeds apredetermined business risk threshold, thus providing identifiedcritical information sources. The method also includes providing atdesign time, fault tolerance to those processes dependent on identifiedcritical information sources. The method further includes detecting atrun time, by the process development and run time tool, informationsource failures of particular information sources, thus designatingparticular failed information sources. The method also includesidentifying at run time, by the process development and run time tool,those processes dependent on the particular failed information sourcesas exhibiting information source defects. The method further includesdisabling at run time, by the process development and run time tool,those processes dependent on the particular failed information sources.The method still further includes communicating at run time, by theprocess development and run time tool, a list of terminated processes tostakeholders of the terminated processes. The method also includesprioritizing at run time, by the process development and run time tool,failures of particular information sources in accordance with businessrisk, the prioritizing at run time designating information sourcefailures as critical information source failures or non-criticalinformation source failures in accordance with the predeterminedbusiness risk threshold. The method further includes bypassing at runtime, by the process development and run time tool, those informationsource defects that correspond to critical information source failures.

In another embodiment, an information handling system (IHS) is disclosedthat includes a processor and information sources coupled to theprocessor. The IHS also includes a memory coupled to the processor. Thememory is configured with a process development and run time tool toform at design time a dependency table that includes a list ofinformation sources with dependent processes, the dependency tablefurther including a list of business values, each business valuecorresponding to a respective dependent process, the dependency tablefurther including a list of business risks, each business riskcorresponding to a respective dependent process, the dependency tablefurther including a respective composite information source businessrisk for each information source in the list of information sources. Theprocess development and run time tool identifies at design time thoseinformation sources of the list of information sources that exhibit acomposite information source business risk that exceeds a predeterminedbusiness risk threshold, thus providing identified critical informationsources. The process development and run time tool also provides atdesign time fault tolerance to those processes dependent on identifiedcritical information sources. The process development and run time toolfurther detects at run time information source failures of particularinformation sources, thus designating particular failed informationsources. The process development and run time tool also identifies atrun time those processes dependent on the particular failed informationsources as exhibiting information source defects. The processdevelopment and run time tool also disables at run time those processesdependent on the particular failed information sources. The processdevelopment and run time tool further communicates at run time a list ofterminated processes to stakeholders of the terminated processes. Theprocess development and run time tool still further prioritizes at runtime failures of particular information sources in accordance withbusiness risk, the prioritizing at run time designating informationsource failures as critical information source failures or non-criticalinformation source failures in accordance with the predeterminedbusiness risk threshold. The process development and run time tool alsobypasses at run time those information source defects that correspond tocritical information source failures.

In yet another embodiment, a process development and run time toolcomputer program product is disclosed. The computer program productincludes a computer readable storage medium. The computer programproduct also includes first program instructions that form at designtime a dependency table that includes a list of information sources withdependent processes, the dependency table further including a list ofbusiness values, each business value corresponding to a respectivedependent process, the dependency table further including a list ofbusiness risks, each business risk corresponding to a respectivedependent process, the dependency table further including a respectivecomposite information source business risk for each information sourcein the list of information sources. The computer program product furtherincludes second program instructions that identify at design time thoseinformation sources of the list of information sources that exhibit acomposite information source business risk that exceeds a predeterminedbusiness risk threshold, thus providing identified critical informationsources. The computer program product still further includes thirdprogram instructions that provide at design time fault tolerance tothose processes dependent on identified critical information sources.The computer program product also includes fourth program instructionsthat detect at run time information source failures of particularinformation sources, thus designating particular failed informationsources. The computer program product further includes fifth programinstructions that identify at run time those processes dependent on theparticular failed information sources as exhibiting information sourcedefects. The computer program product still further includes sixthprogram instructions that disable at run time those processes dependenton the particular failed information sources. The computer programproduct also includes seventh program instructions that communicate atrun time a list of terminated processes to stakeholders of theterminated processes. The computer program product further includeseighth program instructions that prioritize at run time failures ofparticular information sources in accordance with business risk, theprioritizing at run time designating information source failures ascritical information source failures or non-critical information sourcefailures in accordance with the predetermined business risk threshold.The computer program product still further includes ninth programinstructions that bypass at run time those information source defectsthat correspond to critical information source failures. The first,second, third, fourth, fifth, sixth, seventh, eighth and ninth programinstructions are stored on the computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

The appended drawings illustrate only exemplary embodiments of theinvention and therefore do not limit its scope because the inventiveconcepts lend themselves to other equally effective embodiments.

FIG. 1 shows a block diagram of a representative information handlingsystem (IHS) that employs the disclosed process development methodology.

FIG. 2 depicts a block diagram of an enterprise system that employs thedisclosed process development methodology.

FIG. 3 shows an information source and process dependency table that thedisclosed process development method employs.

FIG. 4 depicts a flowchart of an embodiment of the disclosed processdevelopment method that provides design time risk assessment and processdevelopment capability.

FIG. 5 depicts a flowchart of another embodiment of the disclosedprocess development method that provides run time risk assessment andprocess development capability.

DETAILED DESCRIPTION

An enterprise system may employ multiple Information handling systems(IHSs) that typically employ operating systems that execute applicationsor other processes within each IHS. The enterprise system may includemultiple information sources that provide information to executingprocesses in the IHSs of the enterprise system. In other words, aparticular process interprets, consumes, or otherwise employsinformation from an associated information source of the enterprisesystem. An information source may be a database of information, files ona storage media, or any form of information for use by executingprocesses within the enterprise system.

The enterprise system may include one or more stakeholders that rely onor benefit from process outputs of those processes that consumeinformation from information sources. In a business environment,enterprise system resources provide for the development and execution ofbusiness processes or processes that offer business resource benefits asoutput. Designers and other entities may assess the risk, such asbusiness risk, of data failure of processes, information sources, orother resources of the enterprise system. Systems with increasedrobustness or tolerance of information source failures in their processdesign or information source design are of greater value to clients orusers of these systems.

At design time, designers or other entities may model various aspects ofthe enterprise system and evaluate process execution behavior duringsimulation of real world activities. During design evaluation, designersmay expose business risks that relate to processes that rely on or aredependent upon information sources. These dependent information sourcesmay provide useful or critical information to executing processes. Atdesign time, designers employing process development tools may utilizeprocess modeling languages, such as Business Process Modeling Language(BPML) to model process flow. BPML provides process development tools,designers, and other entities access to process execution input andoutput data flow. Designers may introduce real world variables and testprocesses executing within IHS resources to model, evaluate, and improvethe robustness of business process design.

Designers may employ modeling languages, such as Business ProcessExecution Language (BPEL) for modeling of processes executing within anenterprise system or IHS. Designers may employ BPEL or other modelinglanguages to generate information models (IM)s of the enterprise systemfor business process risk or process risk assessment as well as otherreasons.

During design time, the enterprise system model or IM may includemultiple IHSs, information sources, stakeholders, as well as otherenterprise system resources. Business processes may fail due to afailure of an associated information source that the process relies ordepends on. An information source that a particular process depends onfor information is herein referred to as a “dependent informationsource” from which the particular process consumes information. Aprocess that is dependent upon a particular information source forconsuming information is herein referred to as a “dependent process”with respect to that particular information source.

Dependent information sources may fail in more than one manner. Forinstance, an executing process may fail to consume dependent informationsource data due to communication or other resource failures orrestrictions. Defects or errors in information corresponding to adependent information source are cause for another type of dependentinformation source failure. An attempt to extract information orresources from dependent information sources that may exhibit defects isa potential cause of information source failure.

FIG. 1 shows an information handling system 100 including a processdevelopment and run time tool 180 that employs the disclosed processdevelopment methodology. IHS 100 includes a processor 105 that mayinclude multiple processors, processor cores or other processorelements. IHS 100 processes, transfers, communicates, modifies, storesor otherwise handles information in digital form, analog form or otherform. IHS 100 includes a bus 110 that couples processor 105 to systemmemory 125 via a memory controller 115 and memory bus 120. In oneembodiment, system memory 125 is external to processor 105. Systemmemory 125 may be a static random access memory (SRAM) array or adynamic random access memory (DRAM) array. Processor 105 may alsoinclude local memory (not shown) such as L1 and L2 caches (not shown). Avideo graphics controller 130 couples display 135 to bus 110.Nonvolatile storage 140, such as a hard disk drive, CD drive, DVD drive,or other nonvolatile storage couples to bus 110 to provide IHS 100 withpermanent storage of information. I/O devices 150, such as a keyboardand a mouse pointing device, couple to bus 110 via I/O controller 160and I/O bus 155.

One or more expansion busses 165, such as USB, IEEE 1394 bus, ATA, SATA,PCI, PCIE, DVI, HDMI and other busses, couple to bus 110 to facilitatethe connection of peripherals and devices to IHS 100. A networkinterface adapter 170 couples to bus 110 to enable IHS 100 to connect bywire or wirelessly to a network and other information handling systems.In this embodiment, network interface adapter 170 may also be called anetwork communication adapter or a network adapter. While FIG. 1 showsone IHS that employs processor 105, the IHS may take many forms. Forexample, IHS 100 may take the form of a desktop, server, portable,laptop, notebook, netbook, tablet or other form factor computer or dataprocessing system. IHS 100 may take other form factors such as a gamingdevice, a personal digital assistant (PDA), a portable telephone device,a communication device or other devices that include a processor andmemory.

IHS 100 employs an operating system (OS) 190 that may store informationon nonvolatile storage 145. IHS 100 includes a computer program producton digital media 175 such as a CD, DVD or other media. In oneembodiment, a designer or other entity configures the computer programproduct with process development and run time tool 180 software topractice the process development methodology. In practice, IHS 100 maystore process development and run time tool 180 and OS 190 onnonvolatile storage 145 as process development and run time tool 180′and OS 190. When IHS 100 initializes, the IHS loads process developmentand run time tool 180′ and OS 190 into system memory 125 for executionas process development and run time tool 180″ and OS 190′, respectively.In practice, IHS 100 may store a dependency table 300 on non-volatilestorage 140. IHS 100 may load dependency table 300 into system memory125 as dependency table 300′. Process development and run time tool 180may employ dependency table 300 in accordance with the disclosed processdevelopment methodology.

As will be appreciated by one skilled in the art, aspects of thedisclosed process development methodology may be embodied as a system,method or computer program product. Accordingly, aspects of the presentinvention may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module” or “system.” Furthermore, aspects of the present invention maytake the form of a computer program product, such as computer programproduct 175 embodied in one or more computer readable medium(s) havingcomputer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readablestorage medium. A computer readable storage medium may be, for example,but not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of the computer readable storage medium would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the FIG. 4 and FIG.5 flowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, can beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowchart of FIG. 4 and FIG. 5 and/orblock diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart of FIG. 4 andFIG. 5 as described below.

FIG. 2 shows an enterprise business process management system orenterprise system 200. Enterprise system 200 employs IHS 100. IHS 100includes processor development and run time tool 180 and dependencytable 300 to practice the disclosed process development methodology. IHS100 may execute one or more business processes such as process A,process B, process C, . . . process N, wherein N is the total number ofprocesses that execute within IHS 100. Enterprise system 200 includesmultiple information sources, namely information source 1, informationsource 2, . . . information source M wherein M is the total number ofinformation sources. Information source 1, information source 2, . . .information source M each couple to IHS 100 to provide processes 220with information. Processes 220 are processes that consume informationfrom information sources 1, 2, . . . M. Processes 220 includes a groupof executing processes, namely process A, process B, process C . . .process N that consume information from information source 1,information source 2, . . . information source M. In other words, eachof processes 220 may consume information from one or more informationsource, namely information source 1, information source 2, . . .information source M.

In another embodiment of the disclosed process development methodology,one or more of the information sources, namely information source 1,information source 2, . . . information source M, may reside within amemory resource of IHS 100 or other entity of enterprise system 200.Information sources, namely information source 1, information source 2,. . . information source M may reside in other locations (not shown)outside of enterprise system 200. For example, these remote informationsources may be databases on remote servers or other memory or storageresources in remote locations.

When processes 220, that includes executing processes such as process A,process B, process C, . . . process N, requires or consumes informationfrom an information source, that information source is then a “dependentinformation source”. In other words if an executing process, such asprocess A, consumes information from an information source, such asinformation source 1, that information source is then a dependentinformation source with respect to process A. In other words, in thisexample, process A employs dependent information source 1 as a source ofinformation. If process A fails to receive accurate or timelyinformation from dependent information source 1, process A may becomeunstable, shut down, or otherwise require intervention to terminateoperation. In some cases, process A may attempt to repair operationafter failing to receive information from an information source.

As described in more detail below, the higher the business value of aparticular process executing within enterprise system 200, the higherthe value of the particular processes dependent information source.Managing the proper operation of a particular information source is ansignificant aspect of the disclosed process development methodology. Aninformation source may fail due to poor or missing communication betweenthe information source and the consuming process. An information sourcemay fail due to hard drive failure, database failure, and other reasons.If a process, such as those of executing processes of processes 220,requires information from an information source, such as informationsource 1, the communication between IHS 100 and information source 1 maybe important to enterprise system 200 users. A loss or degradation ofcommunication for any reason may cause one or more of executingprocesses of processes 220, and particularly those of critical businessprocesses, to become unstable or produce unwanted or bad results. If theinformation in the dependent information source is defective, similarunstable or bad results may occur for information consuming processes220.

Enterprise system 200 includes an information consumed data structure230. Information consumed data structure 230 provides processdevelopment and run time tool 180 with information corresponding tothose processes and activities that a particular process spawns orinitiates. This information consumed data structure 230 may provideuseful information for the development of process business riskassessment. Enterprise system 200 includes a prioritization of defectsdata structure 240. Prioritization of defects data structure 240provides process development and run time tool 180 input into thedevelopment of information source defect risk assessment andprioritization of information source defects for elimination or otheractions as described in more detail below.

Enterprise system 200 includes a stakeholder IHS 250. The stakeholderIHS 250 is a stakeholder or entity that employs one or more processes ofexecuting processes, namely process A, process B, process C, . . .process N of processes 220. Stakeholder 250 may employ output, provideinput, or otherwise interact with executing processes 220. StakeholderIHS 250 couples to IHS 100. Stakeholder IHS 250 may be an IHS, or anyform of stakeholder or interest in the output of executing processes ofprocesses 220. In one embodiment of the disclosed process developmentmethodology, stakeholder IHS 250 is a system administrator, user,designer or other entity receiving executing processes of processes 220output in a manual method. In another embodiment of the disclosedprocess development methodology, stakeholder IHS 250 may be anotherprocess, such as a business process of enterprise system 200 thatreceives as input the output of one or more process of processes 220.Enterprise system 200 may include multiple stakeholders or stakeholderIHSs. Other stakeholder IHSs may reside in remote locations (not shown)outside of enterprise system 200.

Process development and run time tool 180 may merge or otherwise work incooperation with OS 190, or other business process management tools (notshown) in accordance with the disclosed process development method.Process development and run time tool 180 may integrate or otherwisesupport and enhance the capabilities of existing business managementprocesses and tools of enterprise system 200. Process development andrun time tool 180 may generate or otherwise populate dependency table300 within IHS system memory 125 or other memory of enterprise system200. Process development and run time tool 180 employs the data ofdependency table 300 to assess business risks as these risks pertain toinformation source and process dependencies.

FIG. 3 is a diagram of a representative information source and processdependency table 300. Process development and run time tool 180populates dependency table 300 in accordance with the disclosed processdevelopment methodology. In one embodiment of the disclosed processdevelopment method, process development and run time tool 180 and/ordesigners or other entities populate dependency table 300 during designtime or during enterprise system 200 planning and development.Dependency table 300 includes an “information source” column 310.Dependency table 300 includes information source 1, as shown in column310, row 360. Dependency table 300 includes information source 2 incolumn 310, row 375. As shown in column 310, row 390, dependency table300 includes information source M, wherein M is the total number ofinformation sources in dependency table 300 and enterprise system 200 asdescribed herein. In one embodiment of the disclosed process developmentmethod, process development and run time tool 180 may populateinformation source data of column 310 from multiple information sources.In other words, one information source, such as information source M mayinclude multiple different information source inputs (not shown) fromenterprise system 200.

At design time, dependency and run time tool 180 may populate eachcolumn of information in dependency table 300 respective to informationsource 1, information source 2, . . . information source M, with usefuldependent process and business risk information. Column 320 includes“dependent processes” information corresponding to each informationsource of column 310. Column 320, row 360 includes an entry of processA. This entry describes the dependent relationship between process A andinformation source 1. In other words, process A requires or consumesinformation from information source 1. Stated in another manner, processA has as a dependent information source, information source 1 andinformation source 1 is a dependent information source of process A.Column 320, row 365, includes process B, and column 320, row 370,includes process C. As shown in rows 360, 365 and 370 of column 320,process A, process B and process C are all dependent processes ofinformation source 1.

In a similar fashion, as shown in rows 375 and 380 of column 320,process B and process C are dependent processes of information source 2.Row 390, column 320 shows process N as a dependent process ofinformation source M. Dependency table 300 includes a “business value ofprocess” column 330. At design time, process development and run timetool 180 or other entity may populate business value of process column330 with business value information for each of information source 1,information source 2, . . . information source M, wherein M is the totalnumber of information sources.

Process development and run time tool 180 or other entity may determinethe respective business value for each process of dependent processescolumn 320. Process development and run time tool 180 may determine andpopulate the business value of process data in column 330 in dependencytable 300 from many key factors. These key factors may include monetaryrisk assessment of process outputs, such as those of processes 220.Other key factors that determine business value of process data incolumn 330 include return on investment analysis and critical businessmanagement risk assessment, as well as other factors. Other key businessvalue factors may include criteria such as revenue generation, corporateliability, operational business risk and other factors.

Dependency table 300 includes process business value or “business valueof process” information in column 330. For example, dependency table 300includes a business value 1A in column 330, row 360. Value 1A may be aquantitative or other measure of the business value of a particularbusiness process. In this manner, value 1A as shown in column 330, row360, represents the business value of process A that employs dependentinformation source 1. In other words, value 1A represents one form ofbusiness value that process A provides. Dependency table 300 includes abusiness value 1B in column 330, row 365. Value 1B as shown in column330, row 365, demonstrates the business value of process B employingdependent information source, namely information source 1. Dependencytable 300 includes a business value 1C in column 330, row 370. Value 1Crepresents the business value of process C that employs dependentinformation source 1.

Dependency table 300 includes a business value 2B in column 330, row375. Value 2B may be a quantitative or other measure of a particularprocess business value. In this manner, value 2B represents the businessvalue of process B that employs dependent information source 2. In otherwords, value 2B represents the business value that process B provides.Dependency table 300 includes a business value 2C in column 330, row380. Value 2C as shown in column 330, row 380, demonstrates the businessvalue of process C employing dependent information source, namelyinformation source 2.

Dependency table 300 includes a business value MN in column 330, row390. Value MN represents the business value of process N that employsdependent information source M, wherein M is the total number ofinformation sources, and N is the total number of processes executing inIHS 100. The “business value of process” data in column 330 of FIG. 3demonstrates one form of process business value. Other forms or methodsof demonstrating business value may include enterprise system 200actions, such as business process procedures or other forms of businessvalue determination.

The business value of process values of a particular information sourcemay not completely describe the total or complete business risk of thatparticular information source. Process development and run time tool 180may require other business risk input to determine the complete risk ofa particular information source, and more particularly the business riskof a particular information source failure. Dependency table 300includes “process business risk” column 340 information. Each processbusiness risk entry in column 340 corresponds to a respective process ofdependent processes column 320 and also corresponds to associatedinformation sources in column 310. In one embodiment of the disclosedprocess development methodology, each process business risk entry incolumn 340 exhibits a high, medium, or low risk setting. Processdevelopment and run time tool 180 or other entities may use differentquantitative or other business risk measures and methods to generate theinformation shown in dependency table 300 process business risk column340. In other embodiments of the disclosed process developmentmethodology, process development and run time tool 180 may determinebusiness risk from other information of dependency table 300 than thatof column 340 data, as well as other information of enterprise 200resources.

In one embodiment of the disclosed process development methodology,process development and run time tool 180 quantifies and generates abusiness risk of “high” as shown in column 340, row 360, correspondingto process A, shown in column 320, row 360, and information source 1 asshown in column 310, row 360. Process development and run time tool 180quantifies and generates process business risk measures as shown incolumn 340 for each process of column 320 for information sources shownin column 310. Process development and run time tool 180 or other entitystores that process business risk information in dependency table 300 asshown in FIG. 3 column 340. In one embodiment of the disclosed processdevelopment method, process business risk information shown in column340 represents the risk to a particular system, such as enterprisesystem 200, in the case of a loss of a particular process or loss of aparticular information source.

Dependency table 300 includes a process business risk of “low” as shownin column 340, row 365, that corresponds to process B, shown in column320, row 365, and information source 1 shown in column 310, row 360.Dependency table 300 includes a process business risk of “medium” asshown in column 340, row 370, that corresponds to process C, shown incolumn 320, row 370, and information source 1 shown in column 310, row360. In a similar manner, process development and run time tool 180 orother entity generates and populates dependency table 300 with processbusiness risk information for information source 2 as shown in column340 as well. Dependency table 300 includes a process business risk of“high” as shown in column 340, row 375, that corresponds to process B,shown in column 320, row 375, and information source 2 shown in column310, row 375. Dependency table 300 includes a process business risk of“high” as shown in column 340, row 380, that corresponds to process C,shown in column 320, row 380, and information source 2 shown in column310, row 375.

Dependency table 300 includes a process business risk ofto-be-determined “TBD” as shown in column 340, row 390, that correspondsto process N, shown in column 320, row 390, and information source Mshown in column 310, row 390. In other words, process development andrun time tool 180 may populate the process business risk for process N,and information source M, wherein M is the total number of informationsources, and N is the total number of processes, in a manner consistentwith the teachings of the disclosed process development method.

Process development and run time tool 180 may generate “compositeinformation source business risk level” shown in column 350 for eachinformation source by combining the process business risk information ofcolumn 340 for each information source. Process development and run timetool 180 may interpret the information in column 340 and generate acumulative or other combinational form of measure to produce anaggregate of all process business risk data from column 340 respectiveto each information source as shown in column 310. In this manner,process development and run time tool 180 may generate the compositeinformation source business risk information, as shown in column 350 bycombining business value data of process information from column 330. Inone embodiment of the disclosed process development methodology, processdevelopment and run time tool 180 generates an accumulation of allprocess business risk information, as shown in column 340, for eachinformation source of column 310. In this manner, process developmentand run time tool 180 generates and populates dependency table 300 witha “composite information source business risk” level as shown in column350. This business risk level reflects the risk of information sourcedefects or failure on processes such as those of processes 220 ofenterprise system 200 that consume information from information sources,such as information 1, information 2, . . . information M.

Dependency table 300 includes a composite information source businessrisk of “medium” as shown in column 350, row 360, that corresponds toinformation source 1 as shown in column 310, row 360. In other words,process development and run time tool 180 determines that informationsource 1 provides medium business risk to enterprise system 200 and tothose users or other entities that rely on processes that consumeinformation source 1 data. Stated in another manner, a loss ofinformation source 1, or defect in information source 1 data offers amedium business risk to the enterprise system 200 and stakeholders, suchas stakeholder IHS 250.

Dependency table 300 includes a composite information source businessrisk of “high” as shown in column 350, row 375, that corresponds toinformation source 2 as shown in column 310, row 375. In other words,process development and run time tool 180 determines that informationsource 2 provides high business risk to enterprise system 200 and tothose users or other entities that rely on processes that consumeinformation source 2 data. A loss of information source 2, or defect ininformation source 2 data offers a high business risk to enterprisesystem 200 and stakeholders, such as stakeholder IHS 250. In oneembodiment of the disclosed process development method, processdevelopment and run time tool 180 may generate or otherwise modifycomposite information source business risk information, as shown incolumn 350, with run time feedback, such as failure process rates orother information.

Dependency table 300 includes a composite information source businessrisk of “TBD” as shown in column 350, row 390, that corresponds toprocess N, shown in column 320, row 390, and information source M, asshown in column 310, row 390. In other words, process development andrun time tool 180 may populate the information source business risk forprocess N, and information source M, wherein M is the total number ofinformation sources, and N is the total number of processes, consistentwith the teaching of the disclosed process development method. Processdevelopment and run time tool 180 may determine a particular thresholdor setting for composite information source business risk, as shown incolumn 350. This threshold may provide process development and run timetool 180 a set point to identify those business risks that exhibit acritical or non-critical nature. For example, a composite informationsource business risk of high may be a critical business risk, wherein acomposite information source business risk of medium may be anon-critical business risk.

The flowchart of FIG. 4 and FIG. 5 illustrates the architecture,functionality, and operation of possible implementations of systems,methods and computer program products that perform data packetmanagement in accordance with various embodiments of the presentinvention. In this regard, each block in the flowchart of FIG. 4 andFIG. 5 may represent a module, segment, or portion of code, whichcomprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that, in somealternative implementations, the functions noted in the block may occurout of the order noted in FIG. 4 and FIG. 5. For example, two blocksshown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of FIG. 4 and FIG. 5 and combinations of blocks in theblock diagrams and/or flowchart illustration, can be implemented byspecial purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

FIG. 4 is a flowchart that shows process flow in an embodiment of thedisclosed process development methodology that provides business riskassessment in an IHS. More specifically, the flowchart of FIG. 4 showshow process development and run time tool 180 provides for generation ofbusiness risk criteria and fault tolerance development during designtime for processes that execute within enterprise system 200. Thedisclosed process development method provides for reduction in businessrisk for users of enterprise system 200 by providing at risk informationsource redundancy and establishing or increasing fault tolerant designin dependent processes.

It is useful to detect a potential information source failure prior toinitiating assembly of the process for execution within resources ofenterprise system 200. The earlier that the potential for informationsource failures is identified, the less expensive for designers todesign in tolerance for those potential information source failures.When designers identify the potential for information source failuresearlier, this may decrease the expense to design in tolerance to theseinformation source failures. The disclosed process development methodprovides for the population of dependency table 300 with process valueand business risk values corresponding to each information source ofenterprise system 200. Process development and run time tool 180 orother entity may interpret information from dependency table 300 duringmodeling or design time operations. From this analysis of dependencytable 300 data, process development and run time tool 180 may elect tomodify or otherwise redesign aspects of enterprise system 200. Thisredesign of enterprise system 200 resources may improve fault tolerancecapabilities of processes and information sources and provide for moreefficient utilization of IHS 100 resources during execution of one moreprocesses therein.

For example, in one embodiment of the disclosed process developmentmethodology, a particular stock price information source provides stockprices that may impact stock trading transactions. Process developmentand run time tool 180 may quantify the business risk for a failure ofthat particular stock price information source by many risk factors. Onerisk factor may include the daily revenue and profit from stock tradingtransactions. Another risk factor may include image loss estimates, suchas compensation costs and lawsuit cost that relate to inability toexecute customer stock trade transactions. Another risk factor mayinclude an estimate of operational risk from the inability to manage acorporations own trading positions in the stock market.

To reduce these risk factors, the disclosed process development methodprovides for redundancy in the particular stock price informationsource, such as including secondary sources for stock price informationin case of failure of the primary stock price information source. Thedisclosed process development method may provide for fault tolerancedesign into the stock trading process. For example, one fault toleranceprocess design change may allow a senior floor trader to place tradeorders at market price without using the normal pricing systems. Thenormal pricing systems may be at risk due to their dependency on theparticular stock price information source.

The disclosed design time process development method starts, as perblock 405. In one embodiment, process development and run time tool 180identifies each process dependent information source, as per block 410.For example, process development and run time tool 180 may identify aparticular process, such as process A of processes 220 that exhibits adependent relationship with a particular information source, such asinformation source 1. In this manner, process development and run timetool 180 establishes a dependency relationship between dependentinformation source 1 and dependent process A. If information source 1exhibits a defect, process A may suffer from that defective informationand introduce potential risks to enterprise system 200 and users of thissystem. Referring to FIG. 3, process development and run time tool 180may populate the information in column 310, namely information sourcedata, and column 320, dependent process information thereby identifyingthe process dependent information source.

Process development and run time tool 180 determines and stores thebusiness value for each process, as per block 420. As shown in FIG. 3dependency table 300, process development and run time tool 180 mayidentify and store, as shown in column 330, a business valuecorresponding to each process as shown in column 320. This businessvalue may provide basis for risk weighting in the case of a loss ofinformation source data, such as described in more detail below. Processdevelopment and run time tool 180 quantifies and stores informationsource business risk dependencies, as per block 430. Process developmentand run time tool 180 determines process business risk and populatesdependency table 300 as shown in FIG. 3 column 340.

By use of cumulative methods, or other aggregate means, processdevelopment and run time tool 180 generates composite information sourcebusiness risk data for each information source. Process development andrun time tool 180 determines and stores composite information sourcebusiness risks, as per block 435. In one embodiment, as shown in FIG. 3column 350, process development and run time tool 180 populatesdependency table 300 with a composite business risk, namely a compositeor overall information source business risk, for each information sourceof enterprise system 200. For example, the information source businessrisk in column 350, row 360, for information source 1 in column 310, row360 is medium. The information source business risk in column 350, row375, for information source 2 in column 310, row 375 is high. In otherwords, information source 2 provides a greater risk to enterprise system200 and the users of enterprise system 200 in the case of informationsource 1 defects because of its high composite information sourcebusiness risk than that of a defect of information source 2 thatexhibits a medium composite information source business risk.

Process development and run time tool 180 performs a test to determineif any information source business risk is a critical risk, as per block440. Process development and run time tool 180 may generate a businessrisk threshold that may identify some business risks as critical andother business risks as non-critical. For example, referring to FIG. 3,if any information source business risk data as shown in column 350exhibits a high value, those corresponding information sources arecritical. In this example, information source 1, as shown in column 310,row 360, exhibits a composite information source business risk value ofmedium, as shown in column 350, row, 360, and is a non-critical businessrisk. The corresponding information source, namely information source 1,as shown in column 310, row 360 is a non-critical information source. Inthe case of failure of information source 1, information source 1 is anon-critical information source failure. On the other hand, informationsource 2, as shown in column 310, row 375, exhibits a compositeinformation source business risk value of high, as shown in column 350,row, 375, and is a critical business risk. The corresponding informationsource, namely information source 2, as shown in column 310, row 375 isa critical information source. In the case of failure of informationsource 2, information source 2 is a critical information source failure.

If the information source business risk exhibits a critical risk,process development and run time tool 180 adds redundancy to informationsource design, or fault tolerance to process design, as per block 450.For example, in the case of information source 2, as shown in column310, row 375 of FIG. 3, the composite information source business riskis high as shown in column 350, row 375. In this case, processdevelopment and run time tool 180 may generate redundant informationsource design to reduce the risk of defect or loss of information source2 resources. Process development and run time tool 180 may facilitate acopy of information source 2 into a new information source 2 (not shown)within enterprise system 200. The redundant information source may be aduplicate IHS, duplicate drive, duplicate database, or other redundantmemory store.

Process development and run time tool 180 may re-design the processes ofexecuting processes 200 that are dependent on information source 2, as amethod of fault tolerance design. As shown in FIG. 3, dependency table300 provides a list of processes dependent upon information source 2,namely process B and process C. Process development and run time tool180 may enhance or otherwise provide input into modification of bothprocess B and process C to provide fault tolerance to information source2 defects. For example, process development and run time tool 180 mayidentify alternate process flows within process B and process C thatredirect or reduce the impact of information source 2 defects orfailure.

Modifications to processes for fault tolerance design may include localdata caching of critical information, inclusion of retry operations formissing data, and many other techniques. If the information sourcebusiness risk is non-critical, or after redundancy and fault tolerancedesign, operating system 190 assembles all dependent processes for runtime execution, as per block 460. OS 190 or other resources ofenterprise system 200 assemble or generate executable code (executableprocesses) from all dependent processes, such as shown in FIG. 3, column320 for run time analysis. The disclosed design time process developmentmethodology ends, as per block 480.

Run time of executable processes within enterprise system 200 providesother opportunities for business risk evaluation and reduction. Forexample, upon failure of a particular stock price information source, asdescribed above in a previous example, the disclosed process developmentmethod provides for informing stakeholders, such as stakeholder IHS 250of information source failures. Stakeholder IHS 250 is dependent uponthe resources or data of the particular stock price information source.Stakeholder IHS 250 may initiate emergency actions, such as informingsenior floor traders to begin using alternative trading processes thatare not dependent upon the particular stock price information source.

The particular business process responsible for network banking(netbanking) applications may put up an indicator, such as a billboard,stating that stock trading is not currently possible. The particularbusiness process may initiate calls to VIP trading clients offeringalternative trading routes through the corporation's internal tradingfloor. Self service trading processes may terminate to avoid corruptresults due to faulty or missing stock price data. Stakeholder IHS 250may initiate these and other emergency actions. Due to critical businessrisks, the disclosed process development method may provide for repairof the particular stock price information source as a higher prioritythan the repair of other information sources.

FIG. 5 shows a flowchart that shows process flow in an embodiment of thedisclosed process development methodology that provides business riskassessment and improvement. More specifically, the flowchart of FIG. 5shows how process development and run time tool 180 provides foridentification of business process risk criteria and elimination ofcritical fault causes during run time for processes that execute withinIHS 100. The disclosed process development method minimizes or reducesthe business impact for enterprise system 200 users from informationsource defects or failure.

In more detail, the disclosed process development method provides forthe identification of particular information source failure impact onprocesses dependent upon these particular information sources duringexecution of processes of processes 220. Process development and runtime tool 180 or other entity may inform stakeholders, such asstakeholder IHS 250 that may be impacted by the particular informationsource failure. Process development and run time tool 180 may terminateand eliminate these particular processes that information source defectsimpact as they relate to measurable risk thresholds.

The disclosed run time process development method starts, as per block505. In one embodiment, process development and run time tool 180 teststo determine if any information source fails as per block 510. If noinformation source failure occurs, process development and run time tool180 continues monitoring enterprise system 200 executing processes ofprocesses 220 for such a failure. An information source failure mayoccur because communication between the information source and theconsuming process fails. An information source may also fail if thatinformation source contains a defect in information. For example, aparticular information source may contain the names and addresses ofemployees for a corporation and one or more of those entries may containincorrect information. In this case, the particular information sourceis defective.

Information source failures may occur due to information inconsistencywith respect to processes and activities consuming those informationsources. For example, the information source may be incomplete for therequirements of the consuming process. The information source may failto meet the information requirements of the consuming process. Forexample, the quality of the information source may fail to meet therequirements of the consuming process. The information source and datamay not be available at the time that the consuming process requires. Inone embodiment of the disclosed process development method, processdevelopment and run time tool 180 may not detect particular informationsource failures, but may rather detect that other resources ofenterprise system 200 detect these particular information sourcefailures.

If an information source failure occurs, process development and runtime tool 180 identifies each process dependent on the failedinformation source, as per block 520. For example, if information source2 fails, process development and run time tool 180 may refer todependency table 300 to determine the dependent processes of informationsource 2 thereto. In this case, dependency table 300 shows that bothprocess B and process C are dependent processes associated withinformation source 2. In one embodiment of the disclosed processdevelopment methodology, process development and run time tool 180 mayoutput a list of dependent processes associated with failed informationsource 2 to other resources of enterprise system 200 or otherstakeholders or resources (not shown) outside of enterprise system 200.

To reduce the risk that information source failures pose to stakeholdersand other resources of enterprise system 200, process development andrun time tool 180 may shut down, disable, eliminate, or otherwiseterminate one or more process of executing processes of processes 220.In one embodiment, process development and run time tool 180 terminatesprocesses impacted by information source failures, as per block 530. Forexample, in the case of information source 2 failure, processdevelopment and run time tool 180 terminates dependent process B anddependent process C. In this manner, process development and run timetool 180 removes the risk of process B and process C providing defectiveoutput to users or consumers of process information of enterprise system200. In another embodiment of the disclosed process developmentmethodology, process development and run time tool 180 does not directlyterminate failed processes. However, process development and run timetool 180 does inform stakeholders, such as stakeholder IHS 250 or otherresources of enterprise system 200 of the failed information source andprovides for user intervention or other means of termination of highrisk dependent processes.

Process development and run time tool 180 informs process stakeholdersof terminated processes, as per block 540. In other words, once aprocess terminates, process development and run time tool 180 broadcaststhis termination condition to resources of enterprise system 200 andmore specifically to all stakeholders, such as stakeholder IHS 250.Stakeholder IHS 250 or other stakeholders (not shown) may requireimmediate or emergency action to eliminate or reduce the business riskfrom any particular information source failure. Process development andrun time tool 180 prioritizes information source defects, as per block545. For example process development and run time tool 180 may determinethe business risk for each information source, as shown in dependencytable 300 column 340.

Process development and run time tool 180 prioritizes elimination ofinformation source defects by business risk, as per block 550. Forexample, process development and run time tool 180 may use theinformation source business risk data as shown in FIG. 3 column 350 todetermine those information source failures that are high enough risk toconsider for elimination. In one embodiment of the disclosed method,process development and run time tool 180 may determine any informationsource failure that corresponds to an information source business riskvalue of “high” as critical. Process development and run time tool 180may then prioritize the failed information source, such as informationsource 2, as shown in FIG. 3 column 310, row 375, for elimination.

Process development and run time tool 180 may eliminate informationsource defects of a particular information source without elimination ofthe information source itself by bypassing defective information of theparticular information source, or other techniques of information defectelimination. For example, process development and run time tool 180 mayuse backup information, such as other data stores that providereplacement for the information source defect. Process development andrun time tool 180 may use other criteria, such as business criticalityof dependent processes, business criticality of the failed informationsource, or other measures for determining elimination of failedinformation source defects and elimination priority. Process developmentand run time tool 180 may use data from prioritization of defects datastructure 240 or other information during prioritization of informationsource defect elimination.

Using the elimination information source defect priority, users or otherentities eliminate prioritized information source defects that exceed aparticular business risk threshold, as per block 560. In one embodiment,process development and run time tool 180 may eliminate prioritizedinformation source defects that exceed a particular business riskthreshold. A user or other entity may identify a business risk of highas the business risk threshold. In this case, if information source 2fails, then the user or other entity eliminates information source 2defects by shutting that corresponding information source down orotherwise eliminating or isolating that defective information sourcecontent from other resources of enterprise system 200. In one embodimentof the disclosed process development method, users or other entities ofenterprise system 200 may terminate or otherwise eliminate processesthat consume prioritized information source defects that exceed apredetermined business risk threshold. The disclosed run time processdevelopment methodology ends, as per block 580.

The above method provides for a run time system that exhibits recoverycapability from information source failure. In one embodiment,alternative process flow for dependent processes associated with failedinformation sources may provide continued flow of dependent processes.In this example, the disclosed method may provide for alternativeinformation sources as redundant information sources. Executingdependent process may employ redundant information sources so thatprocessing may continue without interruption of services tostakeholders, resources, and other users of enterprise system 200.

As will be appreciated by one skilled in the art, aspects of thedisclosed process development management technology may be embodied as asystem, method, or computer program product. Accordingly, aspects of thepresent invention may take the form of an entirely hardware embodiment,an entirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module” or “system.” Furthermore, aspects of the present invention maytake the form of a computer program product embodied in one or morecomputer readable medium(s) having computer readable program codeembodied thereon.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The invention claimed is:
 1. A method, comprising: forming at designtime, by a process development and run time tool executing on aprocessor in an information handling system (IHS), a dependency tablestored in the IHS that includes a list of information sources withdependent processes, the dependency table further including a list ofbusiness values, each business value corresponding to a respectivedependent process, the dependency table further including a list ofbusiness risks, each business risk corresponding to a respectivedependent process, the dependency table further including a respectivecomposite information source business risk for each information sourcein the list of information sources, wherein the composite informationsource business risk for each given information source is generatedbased on the list of business values for the dependent processes of thegiven information source and the list of business risks for thedependent processes of the given information source; identifying atdesign time, by the process development and run time tool in the IHS,those information sources of the list of information sources in thedependency table that exhibit a composite information source businessrisk that exceeds a predetermined business risk threshold, thusproviding identified critical information sources; modifying at designtime by the IHS, processes from the dependency table that are dependenton identified critical information sources to provide fault tolerance tothose processes, wherein the fault tolerance includes local caching ofthe processes dependent on the identified critical information sources;adding redundancy to identified critical information sources;assembling, at design time by the IHS, the modified processes for runtime analysis; executing the processes and modified processes in the IHSthat receive information from the information sources; detecting at runtime, by the process development and run time tool in the IHS,information source failures, thus designating failed informationsources; identifying at run time, by the process development and runtime tool in the IHS, those processes or modified processes executing ona processor in the IHS dependent on the failed information sources,based on the dependency table, as exhibiting information source defects;terminating at run time, by the process development and run time tool inthe IHS, execution of those processes or modified processes dependent onthe failed information sources, thus providing terminated processes;communicating at run time, by the process development and run time toolin the IHS, a list of the terminated processes, identified from thedependency table, to stakeholders of the terminated processes;prioritizing at run time, by the process development and run time toolin the IHS, failed information sources in accordance with the compositeinformation source business risk, the prioritizing at run timedesignating particular failed information sources as criticalinformation source failures or non-critical information source failuresin accordance with the predetermined business risk threshold; andbypassing at run time, by the process development and run time tool inthe IHS, those failed information sources that correspond to criticalinformation source failures, the bypassing of the particular failedinformation sources being achieved by replacing information sourcedefects with backup information from data stores.
 2. The method of claim1, wherein the predetermined business risk threshold is associated withcritical business risk.
 3. The method of claim 1, wherein theidentifying at run time step comprises accessing, by the processdevelopment and run time tool, the dependency table to determine thoseprocesses dependent on the particular information source.
 4. Aninformation handling system (IHS), comprising: a processor; informationsources coupled to the processor; a memory coupled to the processor, thememory being configured with a process development and run time tool,wherein the process development and run time tool executes on theprocessor to: form at design time a dependency table stored in the IHSthat includes a list of information sources with dependent processes,the dependency table further including a list of business values, eachbusiness value corresponding to a respective dependent process, thedependency table further including a list of business risks, eachbusiness risk corresponding to a respective dependent process, thedependency table further including a respective composite informationsource business risk for each information source in the list ofinformation sources, wherein the composite information source businessrisk for each given information source is generated based on the list ofbusiness values for the dependent processes of the given informationsource and the list of business risks for the dependent processes of thegiven information source; identify at design time those informationsources of the list of information sources in the dependency table thatexhibit a composite information source business risk that exceeds apredetermined business risk threshold, thus providing identifiedcritical information sources; modify at design time processes from thedependency table that are dependent on identified critical informationsources to provide fault tolerance to those processes, wherein the faulttolerance includes local caching of the processes dependent on theidentified critical information sources; add redundancy to identifiedcritical information sources; assemble, at design time by the IHS, themodified processes for run time analysis; execute the processes andmodified processes in the IHS that receive information from theinformation sources; detect at run time information source failures,thus designating failed information sources; identify at run time thoseprocesses or modified processes executing on a processor in the IHSdependent on the failed information sources, based on the dependencytable, as exhibiting information source defects; terminate at run timeexecution of those processes or modified processes dependent on thefailed information sources, thus providing terminated processes;communicate at run time a list of the terminated processes, identifiedfrom the dependency table, to stakeholders of the terminated processes;prioritize at run time failed information sources in accordance with thecomposite information source business risk, the prioritizing at run timedesignating particular failed information sources as criticalinformation source failures or non-critical information source failuresin accordance with the predetermined business risk threshold; and bypassat run time those particular failed information sources that correspondto critical information source failures, the bypassing of the particularfailed information sources being achieved by replacing informationsource defects with backup information from data stores.
 5. The IHS ofclaim 4, wherein the predetermined business risk threshold is associatedwith critical business risk.
 6. The IHS of claim 4, wherein the processdevelopment and run time tool accesses the dependency table at run timeto determine those processes dependent on the particular informationsource.
 7. A process development and run time tool computer programproduct, comprising: a non-transitory computer readable storage medium;first program instructions that, when executed by a processor in aninformation handling system (IHS), form at design time a dependencytable stored in the IHS that includes a list of information sources withdependent processes, the dependency table further including a list ofbusiness values, each business value corresponding to a respectivedependent process, the dependency table further including a list ofbusiness risks, each business risk corresponding to a respectivedependent process, the dependency table further including a respectivecomposite information source business risk for each information sourcein the list of information sources, wherein the composite informationsource business risk for each given information source is generatedbased on the list of business values for the dependent processes of thegiven information source and the list of business risks for thedependent processes of the given information source; second programinstructions that, when executed by a processor, identify at design timethose information sources in the dependency table that exhibit acomposite information source business risk that exceeds a predeterminedbusiness risk threshold, thus providing identified critical informationsources; third program instructions that, when executed by a processor,modify at design time processes from the dependency table that aredependent on identified critical information sources to provide faulttolerance to those processes, wherein the fault tolerance includes localcaching of the processes dependent on the identified criticalinformation sources; fourth program instructions that, when executed bya processor, add redundancy to identified critical information sources;fifth program instructions that, when executed by a processor, assembleat design time the modified processes for run time analysis; sixthprogram instructions that, when executed by a processor, execute theprocesses and modified processes in the IHS that receive informationfrom the information sources; seventh program instructions that, whenexecuted by a processor, detect at run time information source failures,thus designating failed information sources; eighth program instructionsthat, when executed by a processor, identify at run time those processesor modified processes executing on a processor in the IHS dependent onthe particular failed information sources, based on the dependencytable, as exhibiting information source defects; ninth programinstructions that, when executed by a processor, terminate at run timeexecution of those processes or modified processes dependent on thefailed information sources, thus providing terminated processes; tenthprogram instructions that, when executed by a processor, communicate atrun time a list of the terminated processes, identified from thedependency table, to stakeholders of the terminated processes; eleventhprogram instructions that, when executed by a processor, prioritize atrun time particular failed information sources in accordance with thecomposite information source business risk, the prioritizing at run timedesignating particular failed information sources as criticalinformation source failures or non-critical information source failuresin accordance with the predetermined business risk threshold; andtwelfth program instructions that, when executed by a processor, bypassat run time those particular failed information sources that correspondto critical information source failures, the bypassing of the particularfailed information sources being achieved by replacing informationsource defects with backup information from data stores, wherein thefirst, second, third, fourth, fifth, sixth, seventh, eighth, ninth,tenth, eleventh, and twelfth program instructions are stored on thenon-transitory computer readable storage medium.
 8. The processdevelopment and run time tool computer program product of claim 7,wherein the predetermined business risk threshold is associated withcritical business risk.
 9. The process development and run time toolcomputer program product of claim 7, further comprising tenth programinstructions that access the dependency table at run time to determinethose processes dependent on the particular information source.